Everyone else went to bed, so I hooked everything back up and can't seem to get the error anymore. Coming from a background in IT I realize that sometimes getting out of the car, hopping on one leg running around the car counterclockwise twice and then trying again sometimes is the answer, but I swear what I said below is correct and the application hangs are in my Windows Application Log. But it appears to be working now, so... :-\

Long story short, the key to the problem looks to be the USB port on the back of this laptop is dying and earlier I had the Shuttle plugged into it. I had left the wireless mouse downstairs when poking at it earlier, so had a free USB port on the side to plug the Shuttle into and the problems went away. And seeing as plugging the mouse receiver into the apparently troublesome port in the back results in the mouse going through an endless loop of "New Hardware Found" I'm guessing that's the problem. Sorry for asking before sorting though all the combinations.

-aric.

ps- that said, I'm still kinda curious about the Feed Hold thing, but seeing as this switch has seemingly swapped left and right for me with the Shuttle I'm willing to just live with the change. :-)

--- In DynoMotion@yahoogroups.com, "adatesman" <adatesman@...> wrote:
>
> Hey TK,
>
> First off, sorry to be such a bother lately. I've gotten my head (mostly) around your approach at this point and think I'm happily on my way, but ran into some goofiness with combining the Mach3 Dynomotion and Shuttle plugins. Namely, when I run the Dynomotion plugin it crashes when using the Shuttle.
>
> But here's the thing.... I've got the buttons on the ShuttlePro mapped to select X, Y, Z, A, Zero X, Y, Z, A, Increment the step wheel (the nine at the top), Rapid++, Rapid-- (either side), and they all seem to be fine. The two wheels also work just fine. The lower four buttons I have mapped to Stop, Pause, Reset and Cycle Start. Reset and Cycle Start work just fine, but Stop and Feed Hold (upper and lower left of the bottom four respectively) crash Mach. It would also crash when I used the Ref All button on the primary Mach3 screen (the 1024 screenset), but not when using the individual Ref(axis) buttons on the Diagnostics screen.
>
> IIRC it was a 904 error, but of course poking at it again now it's not happening. Only thing I've changed is I'm not currently hooked up to the Gecko540 and while troubleshooting I had reset the two problem buttons to Zero All (which seems to have avoided the crashes).
>
> I'll be poking at it again tomorrow and will likely be able to confirm the error numbers, but thought I'd run it by you now in case it's something you've run across before. I'm running the current lockdown of Mach3, the current Shuttle plugin and your current plugin.
>
> -aric.
>